PROBLEMS:
My VX2 resets, goes back to VFO, or i get an ERROR immediately when I try to write!

SOLUTION:
The config info in the VX2 does not match what is in the file being sent.

Goto Advanced > Mods
Check Enable Mods.
Read from the VX2. It does not matter what is in the VX2.
Open the file you want to write, and write it to the VX2.

Enabling mods does not actually apply any mods. It only allows your file
config to be changed, based on the last successful read or write to your VX2.




PROBLEM:
I can read from the VX2 just fine, but I cannot write data that I read back to the VX2!
Or
The write seems to go OK at first (RX for a while), but you eventually get a ERROR.

SOLUTION:
On some PCs, the software routine that writes to the VX2 is executing too fast, and 
the VX2 cannot receive the data quick enough. I think this happens mostly on XP. 

To slow it down:

Go To Settings > Port.
Click the "!" button. This will display the "Write Delay" dialog.

The default value is 16. Try higher values to make the write take a little longer (17,20,25, etc).
Increase the value a little, and try to write to the VX2 again. 
However, note that very high values may cause corruption or a clone error.




PROBLEM:
I cannot read from the VX2, no data is received in the status window!

SOLUTION:
If you do not see any response data, then you likely have one of the following problems:

Your cable has a bad connection. Be sure it is FIRMLY plugged into the PC.

Your adapter has a bad connection. Be sure it is FIRMLY connected.

It is possible you may have a bad cable or adapter. If you purchased your cable 
from RT Systems, read the help on their website and use hyperterminal to test your cable.

Your port setting in VX2 Commander is not the one the cable is connected to.
This can be set under Settings > Port. 




PROBLEM:
I have tried to read from the VX2 many times, but I always get an "Invalid
Checksum"!

SOLUTION:
Double check to be sure all of your connections are good.

Try a "Set Mode Reset".

Try a Microprocessor Reset.

Try it on another computer. 

If it does work on the other computer, you may have an issue with your COM port hardware on 
the problem computer.
If it does not work on the other computer, then something is bad between the VX2 and the PC 
(Cable, adapter, etc)

Icom-based two transistor designs may work on some PCs but not on others due to
differences in COM port hardware. If this is a problem for you, build the 
six-transistor design here: 
http://www.icongrp.com/~sllewd/pcware.htm
or purchase a commercially made cable.



PROBLEM:
I encounter the error: "Variable uses Automation type non supported in Visual 
Basic" when trying to use VX2 Commander!

SOLUTION:
Run the included Reg_Xp.exe file. Click "Uninstall" then click "Install".

If VX2 Commander still does not work:

Download the "OLE Automation Update" from here:
http://www.qsl.net/kc8unj/OLE_Update.zip

Unzip it, and install.



PROBLEM:
I receive an error "First Block Too Long" when trying to read from the VX2! 
Every byte in the first block has a "zero byte" after it, such as "0A 00 01 00 02 00 06 00 09 
00 24 00 E3 00 03 00 02 00 24 00"

SOLUTION:
Under Win9X/XP, go into your device manager. Select your COM port, and remove it. Then, re-boot 
and let windows detect it and re-install the driver.
Under WinNT/2K, you may need to manually remove and reinstall the COM port.



PROBLEM:
I encounter errors trying to use VX2 Commander with my USB to serial adapter!

SOLUTION:
Try going into device manager, COM port settings, advanced. Slide both FIFO Buffer sliders all the 
way to the left.

Try another USB to Serial adapter. The following model has been reported to work with one of my other programs, VX7 Commander:

Manufacturer: Belkin
Model#: F5U109
Cost: 29.99
Where: Circuit City (in the PDA section)
Settings: default Com setting, except for FIFO buffers turned all down)












